Druid v1.58
Deployment Dates
The table below lists the deployment date of Druid v1.58 across Druid Clouds. To view the Druid Releases Calendar, see Druid ChatBot Releases.
|
Druid Cloud Community *.community.Druidplatform.com |
Druid Cloud US *.us.Druidplatform.com |
Druid Cloud Australia *au.Druidplatform.com |
Druid Cloud West-Europe (PROD) *.Druidplatform.com |
|---|---|---|---|
| January 20, 2022 | February 17, 2022 | February 17, 2022 | February 17, 2022 |
These release notes give you a brief, high-level description of the improvements implemented to existing features.
If you have questions about your Druid tenant, please contact support@Druidai.com or your local Druid partner for more information.
What's New
- With this release, bot authors can import simple FAQ flows from DialogFlow ES (root level intents with no follow-up intents), putting at your disposal the Dialogflow data source (intents and responses). For more information, see Import QnA flows from DialogFlow ES.
Improvements
- This release introduces dedicated permissions for the following Druid features:
- QnA designer
- Evaluation
- References
- History and logs
- Administration / Druid Services
- Oracle Contact Center live chat conversations are now visible on Dashboards. For that, the following live chat events for Oracle Contact Center integration have been added to live chat activity: client in queue, client connected, transferred and disconnected.
- Druid Hybrid Deployment manual is now available in Druid Connector Host Installer. Clicking Help will open the manual in pdf format.
- UiPath Connector – a new field, Item Priority is now available on AddItemToUiPathQueue integration tasks which allows bot authors to specify the priority level of the queue item to be added. This property is a criterion for the prioritization of queue items. In previous Druid versions, the default priority of queue elements was “Low”.
- Live Chat – When an agent clicks to log out while having ongoing conversations or when engaged in a conversation and automatic allocation is active, a log out request is initiated and the agent will be logged out after all live sessions have ended.
